Update Hono Grafana dashboards from schemaVersion 16 to 38#565
Merged
calohmn merged 1 commit intoeclipse-packages:masterfrom Nov 2, 2025
Merged
Conversation
|
@calohmn anything blocking this pr? |
Contributor
mattkaem
force-pushed
the
dev/feature/update-grafana-dashboards
branch
from
fc24920 to
f51e8b3
Compare
Contributor
Author
I have increased the version number and added a release note |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This Pull Request contains the automatic migration applied by Grafana v10.1.5 to the default Grafana dashboards when deploying the Hono chart with the Grafana dependency (Grafana chart version 6.61.2).
By committing this update now, we eliminate the "noise" of the automatic schema migration.
This makes future changes to the dashboards significantly easier and cleaner as you will only see the diff of your actual functional changes, not the changes from the schema update.